[Benchmark] Upgrade OmniDocBench to v1.5 - #1640
Open
reacher-z wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
OmniDocBenchdatasetOmniDocBench_v1_0Why
The v1.5 TSV already published in
ouyanglinke/OmniDocBench_tsvcannot be evaluated by the current adapter: itsanswercolumn contains Python dictionary literals, sojson.loads()rejects all 1,355 rows. The fallback here usesast.literal_eval; it never executes annotation text.Fixes #1456.
Validation
995f1af5b4e24ad0a6417cbff708b3fcpage_info,layout_dets, andextraschemasload_success=1,load_fail=0py_compile,git diff --check, and all configured pre-commit hooks passImplementation and validation were performed with OpenAI Codex assistance; I reviewed the resulting code, dataset provenance, hashes, and executed checks.